ci: revert "ci: use release token for release (#791)" #795
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reverts commit f686a5a.
ryan-s-roberts
approved these changes
Jul 24, 2025
Pull Request Test Coverage Report for Build 16504211259Details
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit f686a5a.
I don't understand the issue with release-please and the RELEASE_TOKEN Edge & Node provided but for now working around using the GITHUB_TOKEN and being able to release is more important while we figure a longer term solution out.
For context, using the GITHUB_TOKEN, which is what we'd been doing suddenly changed behavior and stopped being able to trigger actions on a PR created by another Action, i.e. the release workflow in GitHub, we need to jimmy it by commit an empty commit for example and that messes up the CHANGELOG 😭